Conversation
docs/concepts_ssr_idp.md
Outdated
| The system requires a reboot for the IDP core allocation; after upgrading to SSR 6.x for the first time, an additional reboot is required to enable the IDP engine. | ||
| ::: | ||
|
|
||
| Software version 6.3.3-R2 introduces the support of multi-core capabilities for IDP for image-based routers. For customers running IDP on older image-based firmware versions (6.3.0-R1 and under) on the SSR1300, SSR1400, and SSR1500, IDP multicore will be automatically enabled when upgrading to 6.3.3-R2. In some cases, after an upgrade the IDP engine can fail to start as it transitions from single-core to multi-core mode. When the IDP engine fails to start, the following alarm will be generated on the system: `IDP engine unable to start; reboot-required`. In this situation, it is recommended to reboot the system post-upgrade to ensure future reliable reboots with IDP multi-core enabled. |
There was a problem hiding this comment.
It is required to reboot to allocate system resources to enable L7-Security (or deallocate on disablement).
| For legacy package-based routers, multi-core IDP capability is not supported, and those systems will continue to operate in the single-core mode. | ||
|
|
||
| :::note | ||
| Multi-core IDP is not supported on the following SSR devices: SSR120, SSR130, and SSR1200. |
There was a problem hiding this comment.
Now that we support AV, and soon SSL Proxy and other features we might want to start calling this advanced L7-Security features or something vs IDP. Not needed for this PR
|
|
||
| <!-- markdown-link-check-disable --> | ||
| 1. On a system that has internet access, use the [ISO Download procedure](intro_downloading_iso.md#downloading-an-iso) to download the `128T-6.3.0-107.r1.el7.OTP.v1.x86_64.iso` from the [6.3 Package Based ISO Download](https://software.128technology.com/artifactory/list/generic-128t-isos-release-local/6.3/) page. | ||
| 1. On a system that has internet access, use the [ISO Download procedure](intro_downloading_iso.md#downloading-an-iso) to download the `128T-6.3.0-107.r1.el7.OTP.v1.x86_64.iso` from the [6.3 Package Based ISO Download](https://software.128technology.com/artifactory/list/generic-128t-isos-release-local/6.3/) page to your device. |
There was a problem hiding this comment.
Since other changes to this document explain the benefits of using 6.3.3 for multi-core L7 security features, this step-by-step guide should be updated to a more recent version of 6.3, specifically 6.3.7.
| 3. Upgrade the conductor using the [Conductor Upgrade procedure](upgrade_ibu_conductor.md). | ||
|
|
||
| 4. Upgrade the conductor using the [Conductor Upgrade procedure](upgrade_ibu_conductor.md). | ||
| 4. Download the `SSR-6.3.0-107.r1.el7.x86_64.ibu-v1.iso` from the [SSR Software Images](https://software.128technology.com/artifactory/list/generic-128t-install-images-release-local) page to your device. <!-- markdown-link-check-enable --> |
There was a problem hiding this comment.
Why does download need to happen twice? Step 1 is also a download.
There was a problem hiding this comment.
The download probably does not need to happen twice. But I'm almost positive that after the conductor is upgraded the ISO needs to be copied onto the conductor again and imported again (on the new partition post-upgrade) in order to make it available to the routers for upgrade.
There was a problem hiding this comment.
Step 1 is downloading the package based install for 6.3.x that has to happen for the conductor to manage image based routers. Step 4 downloads the image based install for the routers.
|
|
||
| <!-- markdown-link-check-disable --> | ||
| 1. On a system that has internet access, use the [ISO Download procedure](intro_downloading_iso.md#downloading-an-iso) to download the `128T-6.3.0-107.r1.el7.OTP.v1.x86_64.iso` from the [SSR ISO Download](https://software.128technology.com/artifactory/list/generic-128t-isos-release-local) page. | ||
| 1. On a system that has internet access, use the [ISO Download procedure](intro_downloading_iso.md#downloading-an-iso) to download the `128T-6.3.0-107.r1.el7.OTP.v1.x86_64.iso` from the [SSR ISO Download](https://software.128technology.com/artifactory/list/generic-128t-isos-release-local) page to your device. |
| 6. [Create a bootable USB](intro_creating_bootable_usb.md) drive from the SSR ISO. | ||
|
|
||
| 7. Import the `SSR-6.1.10-8.lts.el7.x86_64.ibu-v1.iso` ISO onto the conductor. The conductor will act as the software repository for the subsequent router upgrades. Do **not** install this package onto the conductor, only import it. | ||
| 6. Import the `SSR-6.1.10-8.lts.el7.x86_64.ibu-v1.iso` ISO onto the conductor. The conductor will act as the software repository for the subsequent router upgrades. Do **not** install this package onto the conductor, only import it. |
There was a problem hiding this comment.
This looks like it was based on a guide with 6.1 being the latest version at the time. 6.1 is EoS, so this should be updated to 6.3.7 as well.
| @@ -145,17 +137,15 @@ For upgrades of Conductor and Conductor-managed routers to software versions pri | |||
|
|
|||
| In this example workflow, the conductor will be upgraded to 6.2.6, and the routers to 6.1.10. | |||
There was a problem hiding this comment.
We should switch to more recent versions of software for the examples.
|
|
||
| <!-- markdown-link-check-disable --> | ||
| 1. On a system that has internet access, use the [ISO Download procedure](intro_downloading_iso.md#downloading-an-iso) to download the `128T-6.3.0-107.r1.el7.OTP.v1.x86_64.iso` from the [6.3 Package Based ISO Download](https://software.128technology.com/artifactory/list/generic-128t-isos-release-local/6.3/) page. | ||
| 1. On a system that has internet access, use the [ISO Download procedure](intro_downloading_iso.md#downloading-an-iso) to download the `128T-6.3.0-107.r1.el7.OTP.v1.x86_64.iso` from the [6.3 Package Based ISO Download](https://software.128technology.com/artifactory/list/generic-128t-isos-release-local/6.3/) page to your device. |
There was a problem hiding this comment.
I think the addition of "to your device" here is a bit confusing and or does not add much new context. Really the steps are this:
- From outside the air gapped environment where download the ISO from our Internet facing repos
- Get the ISO from that laptop/device into the air gapped environment and copy it onto the conductor. This is a step that the customer should understand how to do, we should not provide additional context for how to do this. But it needs to be done.
- Once the ISO is on the conductor in the air gapped environment, they use the import command to load the software.
4 participants
No description provided.